Systems and methods of detecting scan avoidance events

ABSTRACT

Methods of detecting scan avoidance events during decode sessions are disclosed herein. An example method includes during a timeout period at one or more processors of the symbology scanner, identifying and decoding a transaction affecting indicia on an object in one or more images to obtain a transaction affecting payload; during the timeout period at the one or more processors, identifying one or more visual features in the one or more images; and in response to identifying a non-transaction affecting indicia associated with the one or more visual features, and failing to identify or decode the transaction affecting indicia, determining a potential scan avoidance attempt and generating a scan avoidance alarm signal.

BACKGROUND

In a retail environment, purchasing items typically involves using abarcode reader at a point-of-sale (POS) system to capture images ofbarcodes attached to each item to be purchased, and decoding the imagesto identify each item being purchased. In some cases, retail employeesscan barcodes on each item a customer wishes to purchase, while in othercases, customers scan the barcodes on items they wish to purchase atself-checkout stations.

SUMMARY

In an embodiment, a computer-implemented method for detecting apotential scan avoidance during a timeout period at one or moreprocessors of the symbology scanner, identifying and decoding atransaction affecting indicia on an object in one or more images toobtain a transaction affecting payload; during the timeout period at theone or more processors, identifying one or more visual features in theone or more images; and in response to identifying a non-transactionaffecting indicia associated with the one or more visual features, andfailing to identify or decode the transaction affecting indicia,determining a potential scan avoidance attempt and generating a scanavoidance alarm signal.

In variations of the above embodiment, the method further includes inresponse to successfully identifying and decoding the transactionaffecting indicia to obtain the transaction affecting payload, sendingthe transaction affecting payload to a point-of-sale system foraffecting a transaction for the object.

In variations of the above embodiments, the method further comprises, inresponse to not identifying a non-transaction affecting indiciaassociated with the one or more visual features not determining apotential scan avoidance event.

In variations of the above embodiments, wherein the non-transactionaffecting indicia includes a non-transaction affecting payload havinginformation associated with a weblink.

In another embodiment, a system to detect a scan avoidance event duringa decode session of a symbology reader includes: an imaging assemblyconfigured to capture, during a timeout period, one or more images; abarcode decoder configured to, during the timeout period, determine atransaction affecting payload from a transaction affecting indicia inthe one or more images, and identify a non-transaction affecting indiciain the one or more images; and a scan avoidance event detectorconfigured to (i) in response to identifying the non-transactionaffecting indicia, and failing to determine the transaction affectingpayload, determine a potential scan avoidance attempt, and generating ascan avoidance alarm signal, and (ii) in response to successfullydetermining the transaction affecting payload, send the transactionaffecting payload to a point-of-sale (POS) system to affect atransaction for the object.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a perspective view of an example POS system, inaccordance with aspects of this disclosure.

FIG. 2 illustrates a cross-sectional perspective view of an examplebi-optic barcode reader including a scan avoidance event detector, inaccordance with aspects of this disclosure.

FIG. 3 is a flowchart representative of example methods, logic ormachine-readable instructions for implementing the example scanavoidance event detector of FIG. 1, in accordance with aspects of thisdisclosure.

FIG. 4 is a block diagram of an example logic circuit to implement theexample methods, apparatus, logic, and/or operations described herein.

In the accompanying figures, like reference numerals refer to identicalor functionally similar elements throughout the separate views, togetherwith the detailed description below, are incorporated in and form partof the specification, and serve to further illustrate embodiments ofconcepts that include the claimed invention, and explain variousprinciples and advantages of those embodiments.

Skilled artisans will appreciate that elements in the figures areillustrated for simplicity and clarity and have not necessarily beendrawn to scale. For example, the dimensions of some of the elements inthe figures may be exaggerated relative to other elements to help toimprove understanding of embodiments of the invention. In general, thesame reference numbers will be used throughout the drawing(s) andaccompanying written description to refer to the same or like parts.

The apparatus and method components have been represented whereappropriate by conventional symbols in the drawings, showing only thosespecific details that are pertinent to understanding the embodiments ofthe invention so as not to obscure the disclosure with details that willbe readily apparent to those of ordinary skill in the art having thebenefit of the description herein. Skilled artisans will readilyrecognize from the following discussion that alternate embodiments ofthe structures and methods illustrated herein may be employed withoutdeparting from the principles set forth herein.

DETAILED DESCRIPTION

As a retail employee or customer scans items for purchase, “scanavoidance,” which may be accidental or intentional, may occur. Scanavoidance represents loss of revenue due to theft, accident, misuse,etc. Scan avoidance event alerts can result in a manager, a securityagent, a police officer, etc. becoming involved. Such situations oftenresult in embarrassment, inconvenience, delay, etc. for a shopper.Accordingly, aspects of this disclosure can be used to confirm detectionof scan avoidance events before they are alerted, thereby reducing falsescan avoidance event alerts, thereby, maintaining positive customersentiment and reducing time spent on behalf of a store. Advantageously,the examples disclosed herein achieve such benefits without the use ofexpensive and/or complex neural networks and/or complex image processingthat are currently in use in some retail stores. Such expensive and/orcomplex neural networks may prevent their usage in some retail stores.

Most items being sold in a retail environment include a transactionaffecting indicia representing a transaction affecting payload thatrepresents a multi-digit identification number (e.g., a universalproduct code (UPC), a European article number (EAN), etc.) for an item.The transaction affecting payload is conveyed to a point-of-sale (POS)system for use identifying the item and charging a customer for theitem. Increasingly, manufacturers are additionally includingnon-transaction affecting indicia (e.g., a quick response (QR) code,etc.) representing a non-transaction affecting payload (e.g.,information associated with a weblink, etc.). In some instances, suchnon-transaction affecting indicia are positioned near transactionaffecting indicia. Non-transaction affecting payload are typically notintended for use in charging a customer for the item. Thus, suchnon-transaction affecting indicia or their associated non-transactionaffecting payload need not be conveyed to a POS system. However, anon-transaction affecting payload may be used by the POS system toreference the payload from a transaction-affecting indicia. In someexamples, non-transaction affecting indicia are scanned or read by aperson using, for example, a smartphone, etc., distinct from a POSsystem.

It has been advantageously discovered that when a non-transactionaffecting indicia is identified, but a transaction affecting indicia isnot identified and/or not decodable, then it is likely that a scanavoidance event has occurred, and a store manager can be notified and/oran alert be presented a POS system. In addition to and/or alternative tovisual features in the form non-transaction affecting indicia, anynumber and/or type(s) of other non-transaction affecting visual featuresmay be used to confirm potential scan avoidance events. Exampleadditional on-transaction affecting visual features include, but are notlimited to a non-transaction affecting indicia, a barcode, a QR code,text, a graphic, a logo, a background, an outline, a dimension, aphysical feature, a human body part, etc. Thus, in general, when anytype of non-transaction affecting visual feature is identified during atimeout period, but a transaction affecting indicia is not identifiedand/or not decodable during the same timeout period, then it is likelythat a scan avoidance event has occurred, and a store manager can benotified and/or an alert presented a POS system. Additionally, when avisual feature, such a human body part, is not normally going to includean indicia, then it can be ignored and a scan avoidance event notalerted. An example timeout period represents a time period (e.g., fivehundred milliseconds) during which, it is determined whether anon-transaction affecting indicia is identified and a transactionaffecting indicia is not identified and/or not decodable.

While for ease of discussion, the following disclosure refers tobarcodes, aspects of this disclosure may be used to confirm scanavoidance events for any number and/or type(s) of indicia including, butnot limited to, QR codes, custom codes, etc. Further, while thefollowing disclosure refers to example barcode readers and POS systems,aspects of this disclosure may be used with any number and/or type(s) ofsymbology readers including bi-optical readers, bi-optic readers, etc.for use with any number and/or type(s) of scanners including, forexample, stationary barcode readers, handheld barcode readers,presentation mode barcode readers, etc. Moreover, while example barcodereaders are disclosed in conjunction with POS systems, aspects of thisdisclosure to detect scan avoidance events can be used in conjunctionwith storage systems, inventory systems, etc.

FIG. 1 illustrates a perspective view of an example POS system 100having a workstation 102 with a counter 104 and a bi-optic barcodereader 106 that may be used to implement the example systems and methodsdisclosed herein to determine, confirm, etc. potential scan avoidanceevents when, during a timeout period a non-transaction affecting visualfeature (e.g., a non-transaction affecting indicia, a QR code, abarcode, text, a graphic, a logo, a background, an outline, a dimension,a physical feature, a human body part, etc.), but a transactionaffecting indicia is not identifiable and/or not decodable during thesame timeout period. The POS system 100 is often managed, operated, etc.by a store employee such as a clerk 108. However, in other cases the POSsystem 100 may be a part of a so-called self-checkout lane where insteadof a clerk, a customer is responsible for checking out his or her ownproducts.

The barcode reader 106 includes a first (e.g., lower) housing 112 and asecond (e.g., raised, vertical or tower) housing 114. The lower housing112 includes a top portion 116 with a first optically transmissivewindow 118 positioned therein along a generally horizontal planerelative to the overall configuration and placement of the barcodereader 106. Generally speaking, the top portion 116 includes a removableor a non-removable weigh platter (e.g., an electronic scale configuredto measure/register the weight of objects placed on the top portion116). The top portion 116 is positioned substantially parallel with atop surface of the counter 104. As set forth herein, the phrase“substantially parallel” means +/−30° of parallel and/or accounts formanufacturing tolerances. While in FIG. 1, the counter 104 and the topportion 116 are illustrated as being about co-planar, the top portion116 and the counter 104 may, additionally and/or alternatively, beconsidered as being about parallel. In some examples, the surface of thecounter 104 is raised or lowered relative to the top portion 116, whilethe top portion 116 remains substantially parallel with the top surfaceof the counter 104. The raised housing 114 is configured to extend abovethe top portion 116 and includes a second optically transmissive window120 positioned in a generally upright plane relative to the top portion116 and/or the first optically transmissive window 118. Note thatreferences to “upright” include, but are not limited to, vertical. Thus,as an example, something that is upright may deviate from a verticalaxis/plane by as much as 30°.

In practice, a product, object, item 122, etc., such as for example abottle, is moved, swiped, etc. past the barcode reader 106 such that atransaction affecting indicia (e.g., a barcode 124) associated with theitem 122 is read (e.g., imaged and decoded) through at least one of thefirst optically transmissive window 118 and the second opticallytransmissive window 120. This is particularly done by positioning theitem 122 within fields of view (FOV) of digital imaging sensor(s) (e.g.,a camera 107) housed inside the barcode reader 106 behind the windows116 and 118. Additionally, as the item 122 is moved past the barcodereader 106, the cameras obtain image data of the item 122. In someexamples, the image data is to verify that the item 122 scanned matchesthe barcode 124. The example item 122 also includes an examplenon-transaction affecting visual feature in the form of a QR code 126.

FIG. 2 illustrates a cross-sectional perspective view of an examplebi-optic barcode reader 200 that can be used to implement the barcodereader 106 of FIG. 1, in accordance with embodiments of this disclosure.As shown, the barcode reader 200 includes an example first (e.g., loweror platter) housing portion 202 that supports a generally horizontalweigh platter 204 having a first, generally horizontal window 206. Thebarcode reader 200 is also shown including an example second (e.g.,raised, vertical or tower) housing portion 208 that supports a second,generally vertical optically transmissive window 210. As shown, thefirst window 206 is substantially perpendicular relative to the secondwindow 210. As set forth herein, the phrase “substantiallyperpendicular” means +/−30° of perpendicular and/or accounts formanufacturing tolerances.

To enable imaging data to be obtained by the barcode reader 200, thebarcode reader 200 includes a printed circuit board (PCB) 211 with oneor more imaging assemblies 212, 214 (e.g., cameras). Each of the imagingassemblies 212, 214 includes an imaging sensor having a plurality ofphotosensitive elements that define a substantially flat surface alongwith other components such as a housing and lens(es) for capturing imagedata for a FOV. The arrangement and configuration of the componentsincluding the imaging sensor, the photosensitive elements, the housing,the lens(es) define a specific FOV for each of the imaging assemblies212, 214. As shown, the first imaging assembly 212 is configured tocapture image data over a first FOV 216 and the second imaging assembly214 is configured to capture image data over a second FOV 218. The imagedata captured by the first and second imaging assemblies 212, 214 mayinclude image data representative of an environment in which a barcodeor target may appear. In some examples, the logic circuit 400 of FIG. 4implements the PCB 211. In various examples, the example processesdescribed in reference to PCB 211 and/or, more generally aspects of thePCB 211 may be achieved in hardware, in software, firmware, and/or somecombination thereof.

To identify and decode indicia from images of items, the PCB 211includes any number and/or type(s) of barcode decoder 220. To detectpotential scan avoidance events, the PCB 211 includes an example scanavoidance event detector 222. The scan avoidance event detector 222determines a potential scan avoidance event when any type ofnon-transaction affecting visual feature (e.g., a non-transactionaffecting indicia, a QR code, a barcode, text, a graphic, a logo, abackground, an outline, a dimension, a physical feature, a human bodypart, etc.) is identified during a timeout period, but a transactionaffecting indicia is not identified and/or not decodable during the sametimeout period, it is likely that a scan avoidance event has occurred.When a scan avoidance event is likely, the scan avoidance event detector222 generates a scan avoidance alert signal, alert, notification,report, etc. In some examples, an indication of the generated alertindicating the potential scan avoidance event is presented to a user ofthe barcode reader 200, e.g., via a user interface of a POS system 100.Additionally and/or alternatively, an indication of the generated alertindicating the potential scan avoidance event may be sent to another(e.g., remote) computing device for presentation to an individualdistinct from a user of the barcode reader 200 (e.g., a manager, owner,or other stakeholder associated with the retail environment). Further,the alert may be stored, recorded, etc. for subsequent recall. Alerts,notifications, etc. can be sent, transferred, etc. via any number and/ortype(s) of communication interfaces, devices, networks, etc.

In some examples, generating the alert or notification indicating thepotential scan avoidance event includes capturing an image of a user ofthe barcode reader 200 via another camera distinct from the barcodereader's camera(s) 212, 214. For example, the additional camera may bepositioned and/or angled to capture an image of the face of a useroperating the barcode reader 200. In some examples, a facial recognitionalgorithm may be used to analyze the image of the face of the user toidentify the user associated with the potential scan avoidance event. Inother examples, the image of the face of the user operating the barcodereader 200 may be sent to a computing device associated with a manager,owner, or other stakeholder associated with the retail environment.

In some examples, the barcode decoder 220 and the scan avoidance eventdetector 222 are implemented as one or more modules of machine-readableinstructions executing on a processor or logic device, such as theprocessor 402 of the logic circuit 400 of FIG. 4. Additionally and/oralternatively, the barcode decoder 220 and/or the scan avoidance eventdetector 222 may be implemented by hardware, software, firmware, and/orsome combination thereof.

A flowchart 300 representative of example processes, methods, logic,software, computer- or machine-readable instructions for implementingthe barcode reader 200 and the scan avoidance event detector 222 isshown in FIG. 3. In some examples, the example processes, methods,logic, software, computer- or machine-readable instructions of FIG. 3are carried out during a decode session. The program of FIG. 3 begins atblock 302 when an item 122 enters one or more FOVs of the barcode reader200, for example, captured in one or more original images through one ormore windows 206, 210 (block 302). When an indicia 124 is detected,(block 302) a timeout period is started (block 304). An example timeoutperiod represents a time period (e.g., five hundred milliseconds) duringwhich, it is determined whether a non-transaction affecting indicia 126is identified and a transaction affecting indicia 124 is not identifiedand/or not decodable.

The barcode reader 200 attempts to detect an indicia 124 from one ormore images captured through the one or more FOVs of the barcode reader200 (block 306). The barcode reader 200 attempts to detectnon-transaction affecting indicia 126 associated with non-transactionaffecting visual features from one or more images captured through theone or more FOVs of the barcode reader 200 (block 308). While thetimeout period has not expired (block 310), the barcode reader 200continues attempting to detect transaction affecting indicia 124 andnon-transaction affecting indicia 126 associated with non-transactionaffecting visual features 126 from the one or more images. When thetimeout period expires (block 310), the scan avoidance event detector222 determines whether a transaction affecting indicia 124 was detectedand decodable (block 312). If a transaction affecting indicia 124 wasdetected and successfully decoded (block 312), the payload of thetransaction affecting indicia is conveyed to the POS system 100 (block314). If a non-transaction affecting indicia 126 was not detected (block316), a potential scan avoidance event is not alerted, provided, stored,etc., a scan avoidance alarm signal is not generated (block 318), andcontrol exits from the program of FIG. 3.

Returning to block 316, if a non-transaction affecting indicia 126associated with a non-transaction affecting visual feature was detected(block 316), a potential scan avoidance event is alerted, provided,stored, etc. and a scan avoidance alarm signal is not generated (block320), and control exits from the program of FIG. 3.

Returning to block 312, when a transaction affecting indicia 124 was notdetected (block 312), control exits from the program of FIG. 3.

FIG. 4 is a block diagram representative of an example logic circuitcapable of implementing, for example, the barcode decoder 220, the scanavoidance event detector 222 and/or, more generally, the PCB 211. Thelogic circuit of FIG. 4 is a processing platform 400 capable ofexecuting instructions to, for example, implement operations of theexample methods described herein, as may be represented by theflowcharts of the drawings that accompany this description. Otherexample logic circuits capable of, for example, implementing operationsof the example methods described herein include field programmable gatearrays (FPGAs) and application specific integrated circuits (ASICs).

The example processing platform 400 of FIG. 4 includes an exampleprocessor 402 such as, for example, one or more microprocessors,controllers, and/or any suitable type of processor. The processingplatform 400 of FIG. 4 includes memory (e.g., volatile memory,non-volatile memory) 404 accessible by the processor 402 (e.g., via amemory controller). The processor 402 interacts with the memory 404 toobtain, for example, machine-readable instructions stored in the memory404 corresponding to, for example, the operations represented by theflowcharts and/or examples of this disclosure. Additionally oralternatively, machine-readable instructions corresponding to theexample operations described herein may be stored on one or moreremovable media (e.g., a compact disc (CD), a digital versatile disk(DVD), removable flash memory, etc.) that may be coupled to theprocessing platform 400 to provide access to the machine-readableinstructions stored thereon. The machine-readable instructions may beexecuted by the processor 402 to implement barcode decoder 220 and thescan avoidance event detector 222. The memory 404 may additionally storescan avoidance event alerts at the barcode reader 200, a remote server,etc.

The example processing platform 400 of FIG. 4 also includes a networkinterface 406 to enable communication with other machines via, forexample, one or more networks. The network interface 406 includes anysuitable type of communication interface(s) (e.g., wired and/or wirelessinterfaces) configured to operate in accordance with any suitableprotocol(s). The network interface 406 may be used to communicativelycouple the barcode reader 200 to a remote device.

The processing platform 400 of FIG. 4 also includes input/output (I/O)interfaces 408 to access image data from imaging devices, cameras, theimaging assemblies 212, 214, etc.

Although FIG. 4 depicts the I/O interfaces 408 as a single block, theI/O interfaces 408 may include a number of different types of I/Ocircuits or components that enable the processor 402 to communicate withperipheral I/O devices. Example interfaces 408 include an Ethernetinterface, a universal serial bus (USB) interface, a Bluetooth®interface, a near field communication (NFC) interface, and/or a PCIExpress interface. The peripheral I/O devices may be any desired type ofI/O device such as a keyboard, a display (a liquid crystal display(LCD), a cathode ray tube (CRT) display, a light emitting diode (LED)display, an organic light emitting diode (OLED) display, an in-placeswitching (IPS) display, a touch screen, etc.), a navigation device (amouse, a trackball, a capacitive touch pad, a joystick, etc.), aspeaker, a microphone, a printer, a button, a communication interface,an antenna, etc.

The above description refers to a block diagram of the accompanyingdrawings. Alternative implementations of the example represented by theblock diagram include one or more additional or alternative elements,processes and/or devices. Additionally or alternatively, one or more ofthe example blocks of the diagram may be combined, divided, re-arrangedor omitted. Components represented by the blocks of the diagram areimplemented by hardware, software, firmware, and/or any combination ofhardware, software and/or firmware. In some examples, at least one ofthe components represented by the blocks is implemented by a logiccircuit. As used herein, the term “logic circuit” is expressly definedas a physical device including at least one hardware componentconfigured (e.g., via operation in accordance with a predeterminedconfiguration and/or via execution of stored machine-readableinstructions) to control one or more machines and/or perform operationsof one or more machines. Examples of a logic circuit include one or moreprocessors, one or more coprocessors, one or more microprocessors, oneor more controllers, one or more DSPs, one or more ASICs, one or moreFPGAs, one or more MCUs, one or more hardware accelerators, one or morespecial-purpose computer chips, and one or more SoC devices. Someexample logic circuits, such as ASICs or FPGAs, are specificallyconfigured hardware for performing operations (e.g., one or more of theoperations described herein and represented by the flowcharts of thisdisclosure, if such are present). Some example logic circuits arehardware that executes machine-readable instructions to performoperations (e.g., one or more of the operations described herein andrepresented by the flowcharts of this disclosure, if such are present).Some example logic circuits include a combination of specificallyconfigured hardware and hardware that executes machine-readableinstructions. The above description refers to various operationsdescribed herein and flowcharts that may be appended hereto toillustrate the flow of those operations. Any such flowcharts arerepresentative of example methods disclosed herein. In some examples,the methods represented by the flowcharts implement the apparatusrepresented by the block diagrams. Alternative implementations ofexample methods disclosed herein may include additional or alternativeoperations. Further, operations of alternative implementations of themethods disclosed herein may combined, divided, re-arranged or omitted.In some examples, the operations described herein are implemented bymachine-readable instructions (e.g., software and/or firmware) stored ona medium (e.g., a tangible machine-readable storage medium) forexecution by one or more logic circuits (e.g., processor(s)). In someexamples, the operations described herein are implemented by one or moreconfigurations of one or more specifically designed logic circuits(e.g., ASIC(s)). In some examples the operations described herein areimplemented by a combination of specifically designed logic circuit(s)and machine-readable instructions stored on a medium (e.g., a tangiblemachine-readable medium) for execution by logic circuit(s).

As used herein, each of the terms “tangible machine-readable medium,”“non-transitory machine-readable medium” and “machine-readable storagedevice” is expressly defined as a storage medium (e.g., a platter of ahard disk drive, a digital versatile disc, a compact disc, flash memory,read-only memory, random-access memory, etc.) on which machine-readableinstructions (e.g., program code in the form of, for example, softwareand/or firmware) are stored for any suitable duration of time (e.g.,permanently, for an extended period of time (e.g., while a programassociated with the machine-readable instructions is executing), and/ora short period of time (e.g., while the machine-readable instructionsare cached and/or during a buffering process)).

In the foregoing specification, specific embodiments have beendescribed. However, one of ordinary skill in the art appreciates thatvarious modifications and changes can be made without departing from thescope of the invention as set forth in the claims below. Accordingly,the specification and figures are to be regarded in an illustrativerather than a restrictive sense, and all such modifications are intendedto be included within the scope of present teachings. Additionally, thedescribed embodiments/examples/implementations should not be interpretedas mutually exclusive, and should instead be understood as potentiallycombinable if such combinations are permissive in any way. In otherwords, any feature disclosed in any of the aforementionedembodiments/examples/implementations may be included in any of the otheraforementioned embodiments/examples/implementations.

The benefits, advantages, solutions to problems, and any element(s) thatmay cause any benefit, advantage, or solution to occur or become morepronounced are not to be construed as a critical, required, or essentialfeatures or elements of any or all the claims. The claimed invention isdefined solely by the appended claims including any amendments madeduring the pendency of this application and all equivalents of thoseclaims as issued.

Moreover in this document, relational terms such as first and second,top and bottom, and the like may be used solely to distinguish oneentity or action from another entity or action without necessarilyrequiring or implying any actual such relationship or order between suchentities or actions. The terms “comprises,” “comprising,” “has”,“having,” “includes”, “including,” “contains”, “containing” or any othervariation thereof, are intended to cover a non-exclusive inclusion, suchthat a process, method, article, or apparatus that comprises, has,includes, contains a list of elements does not include only thoseelements but may include other elements not expressly listed or inherentto such process, method, article, or apparatus. An element proceeded by“comprises . . . a”, “has . . . a”, “includes . . . a”, “contains . . .a” does not, without more constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises, has, includes, contains the element. The terms“a” and “an” are defined as one or more unless explicitly statedotherwise herein. The terms “substantially”, “essentially”,“approximately”, “about” or any other version thereof, are defined asbeing close to as understood by one of ordinary skill in the art, and inone non-limiting embodiment the term is defined to be within 10%, inanother embodiment within 5%, in another embodiment within 1% and inanother embodiment within 0.5%. The term “coupled” as used herein isdefined as connected, although not necessarily directly and notnecessarily mechanically. A device or structure that is “configured” ina certain way is configured in at least that way, but may also beconfigured in ways that are not listed.

Further still, unless expressly stated to the contrary, “or” refers toan inclusive or and not to an exclusive or. For example, “A, B or C”refers to any combination or subset of A, B, C such as (1) A alone, (2)B alone, (3) C alone, (4) A with B, (5) A with C, (6) B with C, and (7)A with B and with C. As used herein, the phrase “at least one of A andB” is intended to refer to any combination or subset of A and B such as(1) at least one A, (2) at least one B, and (3) at least one A and atleast one B. Similarly, the phrase “at least one of A or B” is intendedto refer to any combination or subset of A and B such as (1) at leastone A, (2) at least one B, and (3) at least one A and at least one B.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter may lie in less thanall features of a single disclosed embodiment. Thus, the followingclaims are hereby incorporated into the Detailed Description, with eachclaim standing on its own as a separately claimed subject matter.

What is claimed is:
 1. A computer-implemented method for detecting a potential scan avoidance during a decode session using a symbology reader, the method comprising: during a timeout period at one or more processors of the symbology scanner, identifying and decoding a transaction affecting indicia on an object in one or more images to obtain a transaction affecting payload; during the timeout period at the one or more processors, identifying one or more visual features in the one or more images; and in response to identifying a non-transaction affecting indicia associated with the one or more visual features, and failing to identify or decode the transaction affecting indicia, determining a potential scan avoidance attempt and generating a scan avoidance alarm signal.
 2. The method of claim 1, further comprising in response to successfully identifying and decoding the transaction affecting indicia to obtain the transaction affecting payload, sending the transaction affecting payload to a point-of-sale system for affecting a transaction for the object.
 3. The method of claim 1, further comprising, in response to not identifying a non-transaction affecting indicia associated with the one or more visual features not determining a potential scan avoidance event.
 4. The method of claim 1, wherein the non-transaction affecting indicia includes a non-transaction affecting payload having information associated with a weblink.
 5. The method of claim 1, wherein the non-transaction affecting indicia includes a quick response (QR) code.
 6. The method of claim 1, wherein the transaction affecting indicia is encoded according to a first format, and wherein the non-transaction affecting indicia is encoded according to a second decode format different than the first decode format.
 7. The method of claim 1, further comprising: detecting the non-transaction affecting indicia to obtain a non-transaction affecting payload; and at least one of (i) storing the non-transaction affecting payload, or (ii) conveying the non-transaction affecting payload to a point-of-system system.
 8. The method of claim 1, wherein the transaction affecting payload includes an identification number associated with the object.
 9. The method of claim 1, wherein transaction affecting indicia represents a Universal Product Code (UPC) barcode or an European Article Number (EAN) barcode.
 10. The method of claim 1, wherein the one or more visual features include at least one of a barcode, text, a graphic, a logo, a background, an outline, a dimension, a physical feature, or a human body part.
 11. The method of claim 10, wherein the one or more visual features represent information related to the object.
 12. The method of claim 10, wherein the one or more visual features exclude one or more other visual features.
 13. The method of claim 1, wherein the symbology reader is a bi-optic reader having a tower portion with a first field of view and a platter portion with a second field of view, and further comprising capturing the one or more images of the object in at least one of the first field of view, or the second field of view.
 14. The method of claim 1, wherein the symbology reader is at least one of a handheld reader, or a presentation mode reader.
 15. The method of claim 1, further comprising at least one of conveying the scan avoidance alarm signal to a remote device for presentation to an individual distinct from a user of the symbology reader, or presenting the scan avoidance alarm signal a point-of-sale system.
 16. The method of claim 1, further comprising starting the timeout period when an object enters one or more field of views of the symbology reader.
 17. The method of claim 1, further comprising starting the timeout period when the transaction affecting indicia is detected in a field of view of the symbology reader.
 18. A system to detect a scan avoidance event during a decode session of a symbology reader, the system comprising: an imaging assembly configured to capture, during a timeout period, one or more images; a barcode decoder configured to, during the timeout period determine a transaction affecting payload from a transaction affecting indicia in the one or more images, and identify a non-transaction affecting indicia in the one or more images; and a scan avoidance event detector configured to in response to identifying the non-transaction affecting indicia, and failing to determine the transaction affecting payload, determine a potential scan avoidance attempt, and generating a scan avoidance alarm signal, and in response to successfully determine the transaction affecting payload, sending the transaction affecting payload to a point-of-sale (POS) system to affect a transaction for the object.
 19. The system of claim 18, further comprising: a processor; and a tangible machine-readable storage medium storing machine-readable instructions that, when executed by the processor, cause the processor to implement the scan avoidance event detector.
 20. The system of claim 18, wherein the scan avoidance event detector is configured to, in response to successfully identifying and decoding the transaction affecting indicia to obtain the transaction affecting payload, send the transaction affecting payload to a point-of-sale system for affecting a transaction for the object.
 21. The system of claim 18, wherein the scan avoidance event detector is configured to, in response to not identifying a non-transaction affecting indicia associated with the one or more visual features not determine a potential scan avoidance event. 